Aggregation of Resource ReSerVation Protocol (RSVP) Reservations over MPLS TE/DS-TE Tunnels
نویسنده
چکیده
Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract RFC 3175 specifies aggregation of Resource ReSerVation Protocol (RSVP) end-to-end reservations over aggregate RSVP reservations. This document specifies aggregation of RSVP end-to-end reservations over MPLS Traffic Engineering (TE) tunnels or MPLS Diffserv-aware MPLS Traffic Engineering (DS-TE) tunnels. This approach is based on RFC 3175 and simply modifies the corresponding procedures for operations over MPLS TE tunnels instead of aggregate RSVP reservations. This approach can be used to achieve admission control of a very large number of flows in a scalable manner since the devices in the core of the network are unaware of the end-to-end RSVP reservations and are only aware of the MPLS TE tunnels.
منابع مشابه
RSVP-TE daemon for DiffServ over MPLS under Linux
The RSVP-TE daemon for DiffServ over MPLS under Linux project supports the important Internet Engineering Task Force (IETF) standards for the set up of MultiProtocol Label Switching (MPLS, RFC3031) tunnels with DiffServ support (DS, RFC2475) under Linux by using the ReSource reserVation Protocol (RSVP, RFC2205). These tunnels support scalable Quality of Service (QoS) in IP networks. While the p...
متن کاملRSVP Standards Today and the Path Towards a Generic Messenger
The Resource Reservation Protocol (RSVP) specified in RFC2205 has evolved from ST-II (RFC1819) to provide end-to-end QoS signaling services for application data streams. Hosts use RSVP to request a specific quality of service (QoS) reservation from the network for particular application flows. RSVP maintains and refreshes reservation states in routers for a requested QoS application flow. By or...
متن کاملInternet Engineering Task Force (ietf) Requirements for Supporting Customer Resource Reservation Protocol (rsvp) and Rsvp Traffic Engineering (rsvp-te) over a Bgp/mpls Ip-vpn Supporting Rsvp/rsvp-te over Bgp/mpls Ip-vpn Supporting Rsvp/rsvp-te over Bgp/mpls Ip-vpn
Today, customers expect to run triple-play services through BGP/MPLS IP-VPNs. Some service providers will deploy services that request Quality of Service (QoS) guarantees from a local Customer Edge (CE) to a remote CE across the network. As a result, the application (e.g., voice, video, bandwidth-guaranteed data pipe, etc.) requirements for an end-to-end QoS and reserving an adequate bandwidth ...
متن کاملNode-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification Statement
Use of Node-ID based Resource Reservation Protocol (RSVP) Hello messages is implied in a number of cases, e.g., when data and control planes are separated, when TE links are unnumbered. Furthermore, when link level failure detection is performed by some means other than exchanging RSVP Hello messages, use of a Node-ID based Hello session is optimal for detecting signaling adjacency failure for ...
متن کاملNetwork Working Group Generic Aggregate Resource Reservation Protocol (rsvp) Reservations
RFC 3175 defines aggregate Resource ReSerVation Protocol (RSVP) reservations allowing resources to be reserved in a Diffserv network for a given Per Hop Behavior (PHB), or given set of PHBs, from a given source to a given destination. RFC 3175 also defines how endto-end RSVP reservations can be aggregated onto such aggregate reservations when transiting through a Diffserv cloud. There are situa...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
عنوان ژورنال:
- RFC
دوره 4804 شماره
صفحات -
تاریخ انتشار 2007